ESQL: Fix skipping of generative ESQL tests#132390
Merged
alex-spies merged 1 commit intoelastic:mainfrom Aug 4, 2025
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix #132273
Our generative tests skip some faulty queries based on the returned error message.
The error message can sometimes be split into multiple lines with backslashes marking the line boundaries, like in the following example:
This should have been skipped based on the string
optimized incorrectly due to missing references, but this skip was prevented because this string was split across multiple lines.Let's stitch the error message back together before we check if it should be ignored, so that such line splits don't prevent skips.